Exploring the Components of Dynamic Modeling Techniques

Upon defining the terms modeling and simulation, it becomes apparent that there is a wide variety of different models, using different techniques, appropriate for different levels of representation for any one system to be modeled. Selecting an appropriate conceptual modeling technique from those available is an open question for the practitioner. Existing methods for describing techniques do not capture enough information about the expressive potential of those techniques such that an appropriate selection decision can be made. A formal method to describe conceptual modeling techniques that captures enough about the technique to distinguish it from others is identified as a way to address this gap in the body of knowledge. Such a formal method is derived, and is given additional expressive strength in the special area of dynamic components of conceptual modeling techniques. Application of the formal method to actual conceptual modeling techniques is exhibited, and the capacity of the method to also identify the potential for extension of an existing method is also exhibited. Measures of merit, designed to evaluate the derived method, are tested and shown to be satisfied

Applying the levels of conceptual interoperability model in support of integratability, interoperability, and composability for system-of-systems engineering

The Levels of Conceptual Interoperability Model (LCIM) was developed to cope with the different layers of interoperation of modeling & simulation applications. It introduced technical, syntactic, semantic, pragmatic, dynamic, and conceptual layers of interoperation and showed how they are related to the ideas of integratability, interoperability, and composability. The model was successfully applied in various domains of systems, cybernetics, and informatics

Composable M&S web services for net-centric applications

Service-oriented architectures promise easier integration of functionality in the form of web services into operational systems than is the case with interface-driven system-oriented approaches. Although the Extensible Markup Language (XML) enables a new level of interoperability among heterogeneous systems, XML alone does not solve all interoperability problems users contend with when integrating services into operational systems. To manage the basic challenges of service interoperation, we developed the Levels of Conceptual Interoperability Model (LCIM) to enable a layered approach and gradual solution improvements. Furthermore, we developed methods of model-based data engineering (MBDE) for semantically consistent service integration as a first step. These methods have been applied in the U.S. in collaboration with industry resulting in proofs of concepts. The results are directly applicable in a net-centric and net-enabled environment

An Extended Interoperability Framework for Joint Composability

Interoperation of systems is defined by the aspects of integratability, interoperability, and composability. It is therefore needed, to address all levels of interoperation - from conceptual models via implemented systems to the supported infrastructure - accordingly in an interoperation framework. Several candidates are available and provide valuable part solution. This paper evaluates the Base Object Models (BOMs), Discrete Event Simulation Specifications (DEVS), Unified Language Model (UML) artifacts as used within the Test and Training Enabling Architecture (TENA), the Object-Process Methodology (OPM), and Conceptual Graphs (CG) regarding their contribution. Using the Levels of Conceptual Interoperability Model (LCIM), an extended interoperability framework based on the contributions of BOM, DEVS, UML/TENA, OPM, and CG will be proposed and gaps in support of joint composability are indentified

Filling the Ontology Space for Coalition Battle Management Language

The Coalition Battle Management Language is a language for representing and exchanging plans, orders, and reports across live, constructive and robotic forces in multi-service, multi-national and multi-organizational operations. Standardization efforts in the Simulation Interoperability Standards Organization seek to define this language through three parallel activities: (1) specify a sufficient data model to unambiguously define a set of orders using the Joint Command, Control, and Consultation Information Exchange Data Model (JC3IEDM) as a starting point; (2) develop a formal grammar (lexicon and production rules) to formalize the definition of orders, requests, and reports; (3) develop a formal battle management ontology to enable conceptual interoperability across software systems. This paper focuses on the third activity, development of a formal battle management ontology, by describing an ontology space for potential technical approaches. An ontology space is a notional three dimensional space with qualitative axes representing: (1) the Ontological Spectrum; (2) the Levels of Conceptual Interoperability Model; and (3) candidate representation sources that can contribute to conceptual interoperability for the Coalition Battle Management Language. The first dimension is the Ontological Spectrum, which shows increasing levels of semantic formalism using various ontology representation artifacts. The second dimension is the Levels of Conceptual Interoperability Model, which describes varying levels of interoperability that can be attained across systems. The third dimension is a survey of likely candidate sources to provide the representation elements required for interoperability. This third dimension will be further described in relation to the artifact capabilities of the second dimension and the conceptual interoperability capabilities of the first dimension to highlight what is possible for ontological representation in C-BML with existing sources, and what needs to be added. The paper identifies requirements for building the ontology artifacts (starting with a controlled vocabulary) for conceptual interoperability, the highest level described in the LCIM, and gives a path ahead for increasingly logical artifacts

C2IEDM for the GIG: A Tutorial

(with Chuck Turnitsa, ODU/VMASC), Spring Simulation Interoperability Workshop, San Diego CA, 3 April 2005Simulation Interoperability Standards Organization (SISO) SIW Conference Pape

Exploring Primitives of Meaning in Support of Interoperability

Semantic mismatch between systems is due, in part, to the grouping together of terms who have defined meaning in different levels of granularity, and which are composed together into different groupings by distinct systems. It has been proposed that making use of elemental concepts (referred to here as primitives of meaning) can assist in interoperability, but seeking to define all terms at a level of granularity equal to or greater than that of all involved systems. By decomposing a system’s groups of composed terms into primitives of meaning, the building blocks that can be reassembled into the compositions required by another group (of another system, for instance) can be made apparent. While such a de-composition could serve as the basis for an interoperability enabler, having the decomposition available as a common descriptor to highlight areas of semantic misalignment should prove in itself useful. Taking doctrinal statements for US small unit infantry actions as one semantic system, we show how the elemental ideas that are grouped together into commands can be identified and isolated for reconstruction into other groupings. This is the first research step towards relying on primitives of meaning for interoperability

Software Reuse for Modeling and Simulation

In Modeling and Simulation, as a distinct area of software engineering, there is much interest in being able to reuse software components. However, the practice of simulation development and maintenance is different from software engineering because of several factors. In this paper, a brief overview of the foundations of interoperability, and how they apply to the reuse of model based software is explored, as well as examination of current practices to include M&S software repositories. Some recommendations, based on research at the Virginia Modeling Analysis and Simulation Center (VMASC) and practice at the Raytheon Company Network Centric Services, are made